Skip to content
This repository was archived by the owner on May 30, 2024. It is now read-only.

Conversation

@drichelson
Copy link
Contributor

No description provided.

@drichelson drichelson closed this Apr 9, 2016
@drichelson
Copy link
Contributor Author

wrong base branch

compile "com.google.guava:guava:19.0"
compile "org.slf4j:slf4j-api:1.7.7"
compile "com.launchdarkly:okhttp-eventsource:0.1.0"
compile group: "com.launchdarkly", name: "okhttp-eventsource", version: "0.1.3-SNAPSHOT", changing: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this do exactly? Never encountered this before.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From here: https://discuss.gradle.org/t/how-to-get-gradle-to-download-newer-snapshots-to-gradle-cache-when-using-an-ivy-repository/7344

In short it goes with the addition on lines 8-12. We're instructing gradle to always go look in a repo for the latest version of this dep. When this is pinned to a stable 1.0.0 it won't be needed, but is very handy for local development and potentially build/deploy systems that that might have older snapshots cached.

I am not a gradle expert, so this might not be the best way to do it.

@jkodumal
Copy link
Contributor

jkodumal commented Apr 9, 2016

Yah, realized that after making a few comments. Can you re-target the other branch?

@drichelson
Copy link
Contributor Author

Github won't let you do this: http://stackoverflow.com/questions/24159036/how-to-modify-a-pull-request-on-github-to-change-target-branch-to-merge-into

I'll address your comments here and in the correct one.

@jkodumal
Copy link
Contributor

jkodumal commented Apr 9, 2016

Yep. We usually just close the PR and open a new one. BTW, BitBucket does
allow this, which is another reason some of us prefer BB.

On Sat, Apr 9, 2016 at 9:26 AM, Dan Richelson notifications@github.com
wrote:

Github won't let you do this:
http://stackoverflow.com/questions/24159036/how-to-modify-a-pull-request-on-github-to-change-target-branch-to-merge-into

I'll address your comments here and in the correct one.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#43 (comment)

@drichelson
Copy link
Contributor Author

#44 has the correct target branch

eli-darkly added a commit that referenced this pull request Feb 21, 2018
support segments (with genericized feature store)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants